Add Oh My Pi (omp) integration: client entry + extension for deterministic read/write paths - #4
Open
asuan-dev wants to merge 1 commit into
Open
Conversation
asuan-dev
force-pushed
the
feat/omp-integration
branch
2 times, most recently
from
August 9, 2026 19:37
c2968f9 to
e2e5ddf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds first-class support for Oh My Pi (omp), a local-first coding agent with a full MCP client and an extension system. omp was missing from
clients.py(sointegrate omp/integrate --alldid not cover it) and had no documented wiring or deterministic write/read path.Changes
src/compartment/clients.py— newompclient entry (writes~/.omp/agent/mcp.json, stdio, standardmcpServersroot; aliasesoh-my-pi). ~/.omp/mcp.json noted as fallback path.integrations/omp/extension.ts— omp extension giving the deterministic paths the MCP entry alone cannot provide:before_agent_start: recalls project memory into a DATA block (automatic read)context: buffers user turns; flushed to the vault atsession_shutdownand pre-compaction (automatic write, dedup + caps)session.compacting: injects recalled memory into the compaction context so summaries do not drop prior decisionsmemory_search/memory_storeregistered as tools, MCP-independentcompartmentCLI — offline, no new dependencies, silent on failure (never blocks the agent loop)docs/INTEGRATIONS.md— omp section.tests/test_clients.py— omp entry test (resolve, path, snippet shape).Why an extension (not just MCP)
omp has a first-class hook/extension subsystem (
pi.on("tool_result" | "context" | "session.compacting" | ...)). The extension mirrors the Claude Code integration experience: automatic recall at session start and a write path that does not depend on model discretion. The MCP entry works alongside it and shares the same vault.Validation
pytest tests/— 731 passed, 8 skipped (usearch optional dep installed to verify the parity test), 0 failedcompartment integrate ompentry resolves:compartment --vault <vault> --caller omp serveNotes
cp integrations/omp/extension.ts ~/.omp/agent/extensions/compartment.ts(auto-discovered on next omp start).